home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
internet-drafts
/
draft-ietf-frnetmib-fr-02.txt
< prev
next >
Wrap
Text File
|
1993-07-26
|
72KB
|
2,301 lines
Internet Draft Frame Relay Service MIB July 26, 1993
Definitions of Managed Objects
for Frame Relay Service
July 26, 1993
Frame Relay Service MIB Working Group
Tracy A. Brown (editor)
Bell Communications Research
331 Newman Springs Road
Red Bank, NJ 07701
tacox@mail.bellcore.com
1. Status of this Memo
This document is an Internet Draft. Internet Drafts are
working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet
Drafts.
Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or obsoleted
by other documents at any time. It is not appropriate to use
Internet Drafts as reference material or to cite them other
than as a "working draft" or "work in progress."
Please check the I-D abstract listing contained in each
Internet Draft directory to learn the current status of this
or any other Internet Draft.
2. Abstract
This memo defines an extension to the Management Information
Base (MIB) for use with network management protocols in
TCP/IP-based internets. In particular, it defines objects for
managing the Frame Relay Service.
This memo does not specify a standard for the Internet
community.
T. Brown (editor) Expires 1/31/94 [Page 1]
Internet Draft Frame Relay Service MIB July 30, 1993
3. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
o RFC 1442 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of
management.
o RFC 1213 defines MIB-II, the core set of managed objects
for the Internet suite of protocols.
o RFC 1445 which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 which defines the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
T. Brown (editor) Expires 1/31/94 [Page 2]
Internet Draft Frame Relay Service MIB July 30, 1993
4. Object Definitions
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) defined in the SMI. In particular, each object
object type is named by an OBJECT IDENTIFIER, an
administratively assigned name. The object type together with
an object instance serves to uniquely identify a specific
instantiation of the object. For human convenience, we often
use a textual string, termed the descriptor, to refer to the
object type.
T. Brown (editor) Expires 1/31/94 [Page 3]
Internet Draft Frame Relay Service MIB July 30, 1993
5. Overview
These objects are used when the particular media being used to
manage is Frame Relay Service. At present, this applies to
these values of the ifType variable in the Internet-standard
MIB:
frame-relay-service (xx)
This section provides an overview and background of how to use
this MIB and other potential MIBs when managing a Frame Relay
Service.
The following diagram shows the MIB stack that could be
followed for managing a Frame Relay Service. This is only an
example and not meant to be inclusive.
____________________________________________________
| | | | |
| | Frame Relay | SIP | RFC1294 |
| | X.25 MIB | Relay | (no applic.|
| | for IW/Encap.| MIB | MIB) |
| | | | |
| MIB II |-----------------------------------|
| | |
| ifTable | Frame Relay Service MIB |
| ifStackTable |___________________________________|
| | | |
| | Physical Layer MIBs | ATM MIB |
| | e.g., DS1/E1 MIB, |---------|
| | RS232-like MIB | Phy. |
| | | Layer |
| | | MIB |
|--------------|-------------------------|---------|
SCOPE OF MIB:
The Frame Relay Service MIB will only manage the Frame Relay
portion of the network.
This MIB will NOT be implemented on User Equipment (e.g.,
DTE), and the Frame Relay DTE MIB (RFC1315) should be used to
manage those devices.
Frame Relay Service MIB is intended to be used for Customer
T. Brown (editor) Expires 1/31/94 [Page 4]
Internet Draft Frame Relay Service MIB July 30, 1993
Network Management (CNM) of a Frame Relay Network Service. It
provides information that allows end-customers to obtain
performance monitoring, fault detection, and configuration
information about their Frame Relay Service.
By using this and other related MIBs, a customer's NMS can
monitor their PVCs and UNI/NNI logical ports. Internal
aspects of the network (e.g., switching elements, line cards,
and network routing tables) are outside the scope of this MIB.
The Customer's NMS will be able to access the SNMP proxy-agent
within the Frame Relay network using SNMP over UDP over IP
with IP encapsulated in Frame Relay according to RFC1294/ANSI
T1.617 Annex F. The customer thus has a PVC to the SNMP
proxy-agent. Alternate access mechanisms are possible. The
service capabilities include retrieving information and
receiving TRAPs. It is beyond the scope of this MIB to define
managed objects to monitor the physical layer. Existing
physical layer MIBs (e.g., DS1 MIB) and MIB II will be used as
possible. The Frame Relay Service SNMP MIB for CNM will not
contain any managed objects to monitor the physical layer.
This MIB primarily addresses Frame Relay PVCs. This MIB may
be extended at a later time to handle Frame Relay SVCs.
This MIB is only used to manage a single Frame Relay Service
offering from one network. If the customer's PVCs traverse
multiple networks, then the customer needs to poll multiple
network proxy-agents to retrieve their end-to-end view of
their service. This MIB will be implemented on a proxy-agent
architecture within each Frame Relay Service network. See
Figure 1 and the Service Management Architecture [11].
T. Brown (editor) Expires 1/31/94 [Page 5]
Internet Draft Frame Relay Service MIB July 30, 1993
+-------------------------------------+
| Customer Network Management Station |
| (SNMP based) |
+-------------------------------------+
/| /| /|
| | |
UNI / NNI / NNI / UNI
| +-----------+ | +-----------+ | +-----------+ |
| | | | | | | | | |
Originating | | | | | | | | | |Terminating
+--------+ | | Network I | | | Network J | | | Network K | | +--------+
| | | | | | | | | | | | | |
| User A | | | | | | | | | | | | |
| |----| |---| |---| |----| User B |
| | | | | | | | | | | | | |
| ////////////////////////////////////////////////////////////// |
| | | | | | | | | | | | | |
+--------+ | +-----------+ | +-----------+ | +-----------+ | +--------+
| | | |
| | | |
| PVC Segment 1 | PVC Segment 2 | PVC Segment 3 |
|<------------->|<------------->|<------------->|
| |
| Multi-network PVC |
|<--------------------------------------------->|
| NNI = Network-to Network Interface |
UNI = User-to-Network Interface
Figure 1
Multi-network PVC
T. Brown (editor) Expires 1/31/94 [Page 6]
Internet Draft Frame Relay Service MIB July 30, 1993
5.1. Apply MIB II to a Frame Relay Service
Use the System Group to apply to the SNMP proxy-agent, since
the proxy-agent may be monitoring many Frame Relay devices in
one network. System Group applies to only one system. This
group is not instantiated.
sysDescr: ASCII string describing the SNMP proxy-agent.
Can be up to 255 characters long. This field is
generally used to indicate the network providers
identification and type of service offered.
sysObjectID: Unique OBJECT IDENTIFIER (OID) for the SNMP proxy-agent.
sysUpTime: Clock in the SNMP proxy-agent; TimeTicks
in 1/100s of a second. Elapsed type since
the proxy-agent came on line.
sysContact: Contact for the SNMP proxy-agent.
ASCII string of up to 255 characters.
sysName: Domain name of the SNMP proxy-agent, for example,
acme.com
sysLocation: Location of the SNMP proxy-agent.
ASCII string of up to 255 characters.
sysServices: Services of the managed device. The value "2"
which implies that
the Frame Relay network is providing
a subnetwork level service is recommended.
This specifies how the Interfaces Group defined in MIB II
shall be used for the management of Frame Relay based
interfaces, and in conjunction with the Frame Relay Service
MIB module. This memo assumes the interpretation of the
Interfaces group to be in accordance with [10]: "The
interfaces table (ifTable) contains information on the managed
resource's interfaces. Each sub- layer below the internetwork
layer of a network interface is considered an interface."
Thus, the ifTable allows the following Frame Relay-based
interfaces to be represented as table entries:
- Frame Relay interfaces in the Frame Relay equipment (e.g.,
switches, routers or networks) with Frame Relay interfaces.
T. Brown (editor) Expires 1/31/94 [Page 7]
Internet Draft Frame Relay Service MIB July 30, 1993
This level is concerned with generic frame counts and
not with individual virtual connections.
In accordance with the guidelines of ifTable, frame counts per
virtual connection are not covered by ifTable, and is
considered interface specific and covered in the Frame Relay
Service MIB module. In order to interrelate the ifEntries
properly, the Interfaces Stack Group defined in [10] shall be
supported.
Some specific interpretations of ifTable for Frame Relay
follow.
Object Use for the generic Frame Relay layer
====== =========================================
ifIndex Each Frame Relay port is represented by an ifEntry.
ifDescr Description of the Frame Relay interface.
ASCII string describing the UNI/NNI access channel. Can be up to
255 characters long.
ifType The value to be allocated for Frame Relay Service is xx.
ifMtu Set to maximum frame size in octets for this frame relay port.
ifSpeed Peak bandwidth in bits per second available for use.
This could be the speed of the access channel and not
the access rate. Actual user information transfer rate (i.e., access rate) of the
UNI or NNI access channel in bits per second (this is not the clocking
speed). For example, it is 1,536,000 bits per second for a
DS1-based UNI/NNI access
channel and 1,984,000 bits per second for an E1-based UNI/NNI access channel.
ifPhysAddress The primary address for this interface/port
assigned by the Frame Relay interface provider.
An octet string of zero length if no address is
used for this interface.
ifAdminStatus Supports read-only access (initially).
The desired administrative status of the frame relay port.
ifOperStatus The current operational status of the Frame Relay
UNI or NNI access channel.
ifLastChange The elapsed time since the last re-initialization of the port.
The value of sysUpTime at the time the interface entered
its current operational state. If the current state
was entered prior to
the last re-initialization of the local network
management subsystem, then
this object contains a zero value.
ifInOctets The number of received octets.
ifOutOctets The number of transmitted octets.
T. Brown (editor) Expires 1/31/94 [Page 8]
Internet Draft Frame Relay Service MIB July 30, 1993
ifInUcastPkts The number of received unerrored frames.
ifInNUcastPkts Set to 0 since the generic Frame Relay level is
point-to-point.
ifOutUcastpkts The number of frames received for transmission.
[Ed. note: Frame Relay switches provide counts of
transmitted frames and not of frames received
for transmission as required by the ifTable.
This is because the latter counter is
switch architecture dependent.
Comments are requested on this issue.]
ifOutNUcastpkts Set to 0 since the generic Frame Relay level is
point-to-point.
ifInErrors The number of received frames that are
discarded, because of an error. Possible errors can be
the following: the frame relay frames
were too long, had CRC errors, or were HDLC
aborts.
ifInUnknownProtos The number of received frames discarded
due to header content errors which include
unrecognized DLCI values or incorrect
header values.
ifInDiscards [to be specified]
ifOutErrors [to be specified]
ifOutDiscards [to be specified]
ifOutQLen [to be specified]
ifSpecific Set to the OBJECT IDENTIFIER { experimental 45 }.
THIS SECTION WILL BE UPDATED WHEN THE IFMIB WORK IS COMPLETED!
Using the SNMP Group of MIB II is an implementation choice.
5.2. Frame Relay Service MIB Terminology
Access Channel - An access channel generically refers to the
DS1/E1 or DS3/E3-based UNI access channel or NNI access
channel across which frame relay data transits. An access
channel is the access pathway for a single stream of user
data.
Within a given T1 line, an access channel can denote any one
of the following:
o Unchannelized T1 - the entire T1 line is considered an access
T. Brown (editor) Expires 1/31/94 [Page 9]
Internet Draft Frame Relay Service MIB July 30, 1993
channel. Each access channel is comprised of 24 T1 time slots.
o Channelized T1 - an access channel is any one of 24 channels.
Each access channel is comprised of a single T1 time slot.
o Fractional T1 - an access channel is a grouping of N T1 time
slots (NX56/64 Kbps, where N = 1-23 T1 Time slots per FT1 Access
Channel) that may be assigned in consecutive or non-consecutive
order.
Within a given E1 line, a channel can denote any one of the following:
o Unchannelized E1 - the entire E1 line is considered a single
access channel. Each access channel is comprised of 31 E1 time
slots.
o Channelized E1 - an access channel is any one of 31 channels.
Each access channel is comprised of a single E1 time slot.
o Fractional E1 - an access channel is a grouping of N E1 time
slots (NX64 Kbps, where N = 1-30 E1 time slots per FE1 access
channel) that may be assigned in consecutive or non-consecutive
order.
Within a given unformatted line, the entire unformatted line
is considered an access channel. Examples include RS-232,
V.35, V.36 and X.21 (non- switched).
Access Rate - The data rate of the access channel. The speed
of the user access channel determines how rapidly the end user
can inject data into the network.
Bc - The Committed Burst Size (Bc) is the maximum amount of
subscriber data that the network agrees to transfer, under
normal conditions, during a time interval Tc. Bc is offered in
terms of bits.
Be - The Excess Burst Size (Be) is the maximum amount of
uncommitted data in excess of Bc that the network will attempt
to deliver during a time interval Tc. Be is offered in terms
of bits.
CIR - The Committed Information Rate (CIR) is the subscriber
data throughput that the network commits to supporting under
normal network conditions. CIR is averaged over the Committed
T. Brown (editor) Expires 1/31/94 [Page 10]
Internet Draft Frame Relay Service MIB July 30, 1993
Rate Measurement Interval (Tc). CIR is offered in terms of
bits per second.
DLCI - Data Link Connection Identifier
Logical Port - This term is used to model the Frame Relay
"interface" on a device.
NNI - Network to Network Interface
Permanent Virtual Connection (PVC) - A virtual connection that
has its endpoints and bearer capabilities defined at
subscription time.
Time slot (E1) - An octet within the 256-bit information field
in each E1 frame is defined as a time slot. Time slots are
position sensitive within the 256-bit information field.
Fractional E1 service is provided in contiguous or non-
contiguous time slot increments.
Time slot (T1) - An octet within the 192-bit information field
in each T1 frame is defined as a time slot. Time slots are
position sensitive within the 192-bit information field.
Fractional T1 service is provided in contiguous or non-
contiguous time slot increments.
UNI - User to Network Interface
N391 -
N392 -
N393 -
T391 -
T392 -
nT3 -
nN3 -
T. Brown (editor) Expires 1/31/94 [Page 11]
Internet Draft Frame Relay Service MIB July 30, 1993
6. Object Definitions
FRNETSERV-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Gauge32,
Integer32, TimeTicks, experimental FROM SNMPv2-SMI
DisplayString, PhysAddress, RowStatus FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
frnetservMIB MODULE-IDENTITY
LAST-UPDATED "9307302355Z"
ORGANIZATION "IETF Frame Relay Network MIB Working Group"
CONTACT-INFO
" Tracy A. Brown
Bellcore
331 Newman Springs Rd.
Red Bank, NJ 07701 USA
Tel: 1-908-758-2107
Fax: 1-908-758-4177
E-mail: tacox@mail.bellcore.com."
DESCRIPTION
"The MIB module to describe generic objects for
Frame Relay Network Service."
::= { experimental xx }
-- Do I need another experimental OID to identify this MIB module?
frnetserv OBJECT IDENTIFIER ::= { experimental 45 }
frnetservObjects OBJECT IDENTIFIER ::= { frnetserv 1 }
frnetservTraps OBJECT IDENTIFIER ::= { frnetserv 2 }
T. Brown (editor) Expires 1/31/94 [Page 12]
Internet Draft Frame Relay Service MIB July 30, 1993
-- The Frame Relay Service Logical Port Group
-- the Frame Relay Logical Port Group
-- This table is an interface specific addendum
-- to the generic ifTable from MIB-II.
frLportTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrLportEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Logical Port
Information table."
::= { frnetservObjects 1 }
frLportEntry OBJECT-TYPE
SYNTAX FrLportEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay Logical
Port Information table."
INDEX { frLportIfIndex }
::= { frLportTable 1 }
FrLportEntry ::=
SEQUENCE {
frLportIfIndex
Integer32,
frLportNumPlan
INTEGER,
frLportContact
DisplayString,
frLportLocation
DisplayString,
frLportType
INTEGER,
frLportAddrDLCILen
INTEGER,
frLportVCSigProtocol
INTEGER,
frLportVCSigPointer
OBJECT IDENTIFIER
}
T. Brown (editor) Expires 1/31/94 [Page 13]
Internet Draft Frame Relay Service MIB July 30, 1993
frLportIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to
MIB II's ifIndex value for this UNI/NNI
logical port."
::= { frLportEntry 1 }
frLportNumPlan OBJECT-TYPE
SYNTAX INTEGER {
other(1),
e164(2),
x121(3),
none(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the
network address numbering plan for this
UNI/NNI logical port. The network address
is the Object ifPhysAddress. The value
none implies that there is no
ifPhysAddress. The SNMP proxy-agent will
return an octet string of zero length for
ifPhysAddress. The value other means that
an address has been assigned to this
interface, but the numbering plan is not
enumerated here."
::= { frLportEntry 2 }
frLportContact OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the
network contact for this UNI/NNI logical
port."
::= { frLportEntry 3 }
frLportLocation OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..255))
T. Brown (editor) Expires 1/31/94 [Page 14]
Internet Draft Frame Relay Service MIB July 30, 1993
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the
network location for this UNI/NNI logical
port."
::= { frLportEntry 4 }
frLportType OBJECT-TYPE
SYNTAX INTEGER {
uni(1),
nni(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the
type of network interface for this logical
port."
::= { frLportEntry 5 }
frLportAddrDLCILen OBJECT-TYPE
SYNTAX INTEGER {
twoOctets10Bits(1),
threeOctets10Bits(2),
threeOctets16Bits(3),
fourOctets17Bits(4),
fourOctets23Bits(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the
Q.922 Address field length and DLCI length
for this UNI/NNI logical port."
::= { frLportEntry 6 }
frLportVCSigProtocol OBJECT-TYPE
SYNTAX INTEGER {
none(1),
lmi(2),
ansiT1617D(3),
ansiT1617B(4),
ccittQ933A(5)
}
T. Brown (editor) Expires 1/31/94 [Page 15]
Internet Draft Frame Relay Service MIB July 30, 1993
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Local
In-Channel Signaling Protocol that is used for
this frame relay UNI/NNI logical port."
::= { frLportEntry 7 }
frLportVCSigPointer OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object is used as a pointer
to the table that contains the Local In-Channel
Signaling Protocol parameters and errors for
this UNI/NNI logical port. See the Frame Relay
Management VC Signaling Parameters and Errors
Group."
::= { frLportEntry 8 }
T. Brown (editor) Expires 1/31/94 [Page 16]
Internet Draft Frame Relay Service MIB July 30, 1993
-- the Frame Relay Management VC Signaling Group
frMgtVCSigTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrMgtVCSigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay Management VC Signaling
Parameters and Errors table."
::= { frnetservObjects 2 }
frMgtVCSigEntry OBJECT-TYPE
SYNTAX FrMgtVCSigEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay Management VC
Signaling Parameters Errors table."
INDEX { frMgtVCSigIfIndex }
::= { frMgtVCSigTable 1 }
FrMgtVCSigEntry ::=
SEQUENCE {
frMgtVCSigIfIndex
Integer32,
frMgtVCSigProced
INTEGER,
frMgtVCSigUserN391
INTEGER,
frMgtVCSigUserN392
INTEGER,
frMgtVCSigUserN393
INTEGER,
frMgtVCSigUserT391
INTEGER,
frMgtVCSigNetN392
INTEGER,
frMgtVCSigNetN393
INTEGER,
frMgtVCSigNetT392
INTEGER,
frMgtVCSigNetnN4
INTEGER,
frMgtVCSigNetnT3
INTEGER,
T. Brown (editor) Expires 1/31/94 [Page 17]
Internet Draft Frame Relay Service MIB July 30, 1993
frMgtVCSigLinkRelRespErrors
Counter32,
frMgtVCSigProtRespErrors
Counter32,
frMgtVCSigInactiveResps
Counter32,
frMgtVCSigLinkRelInitErrors
Counter32,
frMgtVCSigProtInitErrors
Counter32,
frMgtVCSigInactiveInits
Counter32
}
frMgtVCSigIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to MIB II's
ifIndex value for this UNI/NNI logical port."
::= { frMgtVCSigEntry 1 }
frMgtVCSigProced OBJECT-TYPE
SYNTAX INTEGER {
u2nuser(1),
u2nnet(2),
bidirect(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Local
In-Channel Signaling Procedure that is used for
this UNI/NNI logical port. The UNI/NNI logical
port can be performing user-to-network user-side
procedures, user-to-network network-side
procedures, or bidirectional procedures."
::= { frMgtVCSigEntry 2 }
frMgtVCSigUserN391 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
T. Brown (editor) Expires 1/31/94 [Page 18]
Internet Draft Frame Relay Service MIB July 30, 1993
"The value of this Object identifies the User-side
N391 full status polling cycle value (nN1 for LMI)
for this UNI/NNI logical port. If the logical
port is not performing user-side procedures, then
this value is equal to zero. This applies to Q.933
Annex A, T1.617 Annex D and LMI."
DEFVAL { 6 }
::= { frMgtVCSigEntry 3 }
frMgtVCSigUserN392 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the User-side
N392 error threshold value (nN2 for LMI) for this
UNI/NNI logical port. If the logical port is not
performing user-side procedures, then this value
is equal to zero. This applies to Q.933 Annex A,
T1.617 Annex D and LMI."
DEFVAL { 3 }
::= { frMgtVCSigEntry 4 }
frMgtVCSigUserN393 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the User-side
N393 monitored events count value (nN3 for LMI)
for this UNI/NNI logical port. If the logical
port is not performing user-side procedures, then
this value is equal to zero. This applies to Q.933
Annex A, T1.617 Annex D and LMI."
DEFVAL { 4 }
::= { frMgtVCSigEntry 5 }
frMgtVCSigUserT391 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the User-side
T391 link integrity verification polling timer
value (nT1 for LMI) for this UNI/NNI logical port.
T. Brown (editor) Expires 1/31/94 [Page 19]
Internet Draft Frame Relay Service MIB July 30, 1993
If the logical port is not performing user-side
procedures, then this value is equal to zero. This
applies to Q.933 Annex A, T1.617 Annex D and LMI."
DEFVAL { 10 }
::= { frMgtVCSigEntry 6 }
frMgtVCSigNetN392 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Network-
side N392 error threshold value (nN3 for LMI) for
this UNI/NNI logical port. If the logical port is
not performing network-side procedures, then this
value is equal to zero. This applies to Q.933
Annex A, T1.617 Annex D and LMI."
DEFVAL { 3 }
::= { frMgtVCSigEntry 7 }
frMgtVCSigNetN393 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Network-
side N393 monitored events count value (nN3 for
LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to zero. This
applies to Q.933 Annex A, T1.617 Annex D and LMI."
DEFVAL { 4 }
::= { frMgtVCSigEntry 8 }
frMgtVCSigNetT392 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Network-
side T392 polling verification timer value (nT2
for LMI) for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures, then this value is equal to zero. This
applies to Q.933 Annex A, T1.617 Annex D and LMI."
T. Brown (editor) Expires 1/31/94 [Page 20]
Internet Draft Frame Relay Service MIB July 30, 1993
DEFVAL { 15 }
::= { frMgtVCSigEntry 9 }
frMgtVCSigNetnN4 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Network-
side nN4 maximum status enquires received value
for this UNI/NNI logical port. If the logical
port is not performing network-side procedures or
is not performing lmi procedures, then this value
is equal to zero. This applies only to LMI."
::= { frMgtVCSigEntry 10 }
frMgtVCSigNetnT3 OBJECT-TYPE
SYNTAX INTEGER (0..20)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the Network-
side nT3 timer (for nN4 status enquires received)
value for this UNI/NNI logical port. If the
logical port is not performing network-side
procedures or is not performing lmi procedures,
then this value is equal to zero. This applies
only to LMI."
::= { frMgtVCSigEntry 11 }
frMgtVCSigLinkRelRespErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of local in-channel signaling link
reliability errors (responding to polls) for this
UNI/NNI logical port."
::= { frMgtVCSigEntry 12 }
frMgtVCSigProtRespErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
T. Brown (editor) Expires 1/31/94 [Page 21]
Internet Draft Frame Relay Service MIB July 30, 1993
"The number of local in-channel signaling protocol
errors (responding to polls) for this UNI/NNI
logical port."
::= { frMgtVCSigEntry 13 }
frMgtVCSigInactiveResps OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the channel declared inactive
(responding to polls) (i.e., N392 errors in N393
events) for this UNI/NNI logical port."
::= { frMgtVCSigEntry 14 }
frMgtVCSigLinkRelInitErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of local in-channel signaling link
reliability errors (initiating polls) for this
UNI/NNI logical port."
::= { frMgtVCSigEntry 15 }
frMgtVCSigProtInitErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of local in-channel signaling protocol
errors (initiating polls) for this UNI/NNI logical
port."
::= { frMgtVCSigEntry 16 }
frMgtVCSigInactiveInits OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the channel declared inactive
(initiating polls) (i.e., N392 errors in N393
events) for this UNI/NNI logical port."
::= { frMgtVCSigEntry 17 }
T. Brown (editor) Expires 1/31/94 [Page 22]
Internet Draft Frame Relay Service MIB July 30, 1993
-- The Frame Relay PVC Connection Group
frPVCConnectTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrPVCConnectEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay PVC Connect table. This Table is
used to model a PVC flow in each direction."
::= { frnetservObjects 3 }
frPVCConnectEntry OBJECT-TYPE
SYNTAX FrPVCConnectEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay PVC Connect table."
INDEX { frPVCConnectLocIfIndex, frPVCConnectLocDLCIIndex,
frPVCConnectRemIfIndex, frPVCConnectRemDLCIIndex }
::= { frPVCConnectTable 1 }
FrPVCConnectEntry ::=
SEQUENCE {
frPVCConnectLocIfIndex
Integer32,
frPVCConnectLocDLCIIndex
Integer32,
frPVCConnectRemIfIndex
Integer32,
frPVCConnectRemDLCIIndex
Integer32,
frPVCConnectAdminStatus
INTEGER,
frPVCConnectOperStatus
INTEGER,
frPVCConnectLastChange
TimeTicks,
frPVCConnectMaxFrameSize
Integer32,
frPVCConnectBc
Integer32,
frPVCConnectBe
Integer32,
frPVCConnectCIR
Integer32,
T. Brown (editor) Expires 1/31/94 [Page 23]
Internet Draft Frame Relay Service MIB July 30, 1993
frPVCConnectGenericPointer
OBJECT IDENTIFIER,
frPVCConnectStatus
RowStatus
}
frPVCConnectLocIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to MIB II's
ifIndex value for this local UNI/NNI logical
port."
::= { frPVCConnectEntry 1 }
frPVCConnectLocDLCIIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to the DLCI
value for this local UNI/NNI logical port
PVCConnect."
::= { frPVCConnectEntry 2 }
frPVCConnectRemIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to MIB II's
ifIndex value for the remote UNI/NNI logical port.
If the value is equal to zero, then this remote
logical port is not a frame relay UNI/NNI logical
port."
::= { frPVCConnectEntry 3 }
frPVCConnectRemDLCIIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to the DLCI
value for the remote UNI/NNI logical port PVC. If
T. Brown (editor) Expires 1/31/94 [Page 24]
Internet Draft Frame Relay Service MIB July 30, 1993
the value is equal to zero, then the remote end of
the PVC is not a Frame Relay connection."
::= { frPVCConnectEntry 4 }
frPVCConnectAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
testing(4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this Object identifies the desired
administrative status of this UNI/NNI logical port
PVC. This state is set by an administrative
entity."
::= { frPVCConnectEntry 5 }
frPVCConnectOperStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
testing(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the current
operational status of this UNI/NNI logical port
PVC."
::= { frPVCConnectEntry 6 }
frPVCConnectLastChange OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the PVC
entered its current operational state. If the
current state was entered prior to the last re-
initialization of the proxy-agent, then this
Object contains a zero value."
T. Brown (editor) Expires 1/31/94 [Page 25]
Internet Draft Frame Relay Service MIB July 30, 1993
::= { frPVCConnectEntry 7 }
frPVCConnectMaxFrameSize OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this Object is the size in octets of
the largest frame relay information field for this
PVC in the ingress direction (into the frame relay
network from the local logical port's point of
view). Must be less than or equal to the
corresponding ifMtu for this frame relay UNI/NNI
logical port."
::= { frPVCConnectEntry 8 }
frPVCConnectBc OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this Object is equal to the
committed burst size (Bc) parameter (measured in
bits) in the direction of local to remote for this
UNI/NNI logical port PVC flow."
::= { frPVCConnectEntry 9 }
frPVCConnectBe OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this Object is equal to the excess
burst size (Be) parameter (measured in bits) in
the direction of local to remote for this UNI/NNI
logical port PVC flow."
::= { frPVCConnectEntry 10 }
frPVCConnectCIR OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this Object is equal to the
committed information rate (CIR) parameter
T. Brown (editor) Expires 1/31/94 [Page 26]
Internet Draft Frame Relay Service MIB July 30, 1993
(measured in bits per second) in the direction of
local to remote for this UNI/NNI logical port PVC
flow."
::= { frPVCConnectEntry 11 }
frPVCConnectGenericPointer OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value of this Object is used as a pointer to
the Generic VC Table. This OID should contain the
appropriate ifIndex and vcIndex values for the
Generic VC Table."
::= { frPVCConnectEntry 12 }
frPVCConnectStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this entry in the
frPVCConnectTable. This variable is used to
create new PVCs and to change existing PVCs. This
capability may not be supported for all
implementations."
::= { frPVCConnectEntry 13 }
T. Brown (editor) Expires 1/31/94 [Page 27]
Internet Draft Frame Relay Service MIB July 30, 1993
-- The PVC End-Point Group
frPVCEndptTable OBJECT-TYPE
SYNTAX SEQUENCE OF FrPVCEndptEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Frame Relay PVC End-Point table. This Table
is used to model a PVC end-point. This table
contains the statistics for a PVC end-point."
::= { frnetservObjects 4 }
frPVCEndptEntry OBJECT-TYPE
SYNTAX FrPVCEndptEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Frame Relay PVC Endpt table."
INDEX { frPVCEndptIfIndex, frPVCEndptDLCIIndex }
::= { frPVCEndptTable 1 }
FrPVCEndptEntry ::=
SEQUENCE {
frPVCEndptIfIndex
Integer32,
frPVCEndptDLCIIndex
Integer32,
frPVCEndptRcvdSigStatus
INTEGER,
frPVCEndptInFrames
Counter32,
frPVCEndptOutFrames
Counter32,
frPVCEndptInDEFrames
Counter32,
frPVCEndptOutDEFrames
Counter32,
frPVCEndptInDiscards
Counter32,
frPVCEndptInOctets
Counter32,
frPVCEndptOutOctets
Counter32
}
T. Brown (editor) Expires 1/31/94 [Page 28]
Internet Draft Frame Relay Service MIB July 30, 1993
frPVCEndptIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to MIB II's
ifIndex value for this UNI/NNI logical port."
::= { frPVCEndptEntry 1 }
frPVCEndptDLCIIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The value of this Object is equal to the DLCI
value for this UNI/NNI logical port PVC End-
point."
::= { frPVCEndptEntry 2 }
frPVCEndptRcvdSigStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
none(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this Object identifies the PVC
status received via the local in-channel signaling
procedures for this UNI/NNI logical port PVC.
This Object is only is only pertinent for
bidirectional procedures and user-to-network user
side procedures. For user-to-network network side
procedures, the value of this Object should be
none."
::= { frPVCEndptEntry 3 }
frPVCEndptInFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames received by the network
T. Brown (editor) Expires 1/31/94 [Page 29]
Internet Draft Frame Relay Service MIB July 30, 1993
(ingress) for this UNI/NNI logical port PVC. This
includes any frames discarded by the network due
to submitting more than Bc + Be data or due to any
network congestion recovery procedures."
::= { frPVCEndptEntry 4 }
frPVCEndptOutFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames sent by the network (egress)
regardless of whether they are Bc or Be frames for
this UNI/NNI logical port PVC end-point."
::= { frPVCEndptEntry 5 }
frPVCEndptInDEFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames received by the network
(ingress) for this UNI/NNI logical port PVC which
were treated as excess traffic. Frames which are
sent to the network with DE set to zero are
treated as excess when more than Bc bits are
submitted to the network during the Committed Rate
Measurement Interval (Tc). Excess traffic may or
may not be discarded at the ingress if more than
Bc + Be bits are submitted to the network during
Tc. Traffic discarded at the ingress is not
recorded in frPVCEndptInDeFrames. Frames which
are sent to the network with DE set to one are
also treated as excess."
::= { frPVCEndptEntry 6 }
frPVCEndptOutDEFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames sent by the network (egress)
that were observed to have the DE bit set to one
for this UNI/NNI logical port PVC end-point."
::= { frPVCEndptEntry 7 }
T. Brown (editor) Expires 1/31/94 [Page 30]
Internet Draft Frame Relay Service MIB July 30, 1993
frPVCEndptInDiscards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of frames received by the the network
(ingress) that were discarded due to traffic
enforcement for this UNI/NNI logical port PVC
end-point."
::= { frPVCEndptEntry 8 }
frPVCEndptInOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets received by the network
(ingress) for this UNI/NNI logical port PVC end-
point. This counter should only count octets from
the beginning of the frame relay header field to
the end of user data. If the network supporting
Frame Relay can not count octets, then this count
should be an approximation."
::= { frPVCEndptEntry 9 }
frPVCEndptOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets sent by the network (egress)
for this UNI/NNI logical port PVC End-point. This
counter should only count octets from the
beginning of the frame relay header field to the
end of user data. If the network supporting Frame
Relay can not count octets, then this count should
be an approximation."
::= { frPVCEndptEntry 10 }
T. Brown (editor) Expires 1/31/94 [Page 31]
Internet Draft Frame Relay Service MIB July 30, 1993
-- Frame Relay Network Service TRAPS
frPVCConnectStatusChange NOTIFICATION-TYPE
OBJECTS { frPVCConnectLocIfIndex, frPVCConnectLocDLCIIndex,
frPVCConnectRemIfIndex, frPVCConnectRemDLCIIndex,
frPVCConnectOperStatus, frPVCEndptRcvdSigStatus }
STATUS current
DESCRIPTION
"This trap indicates that the indicated PVC has
changed state. This trap is not sent if an FR-UNI
changes state; a linkDown or linkUp trap should be
sent instead."
::= { frnetservTraps 1 }
T. Brown (editor) Expires 1/31/94 [Page 32]
Internet Draft Frame Relay Service MIB July 30, 1993
-- Conformance Information
frnetservConformance OBJECT IDENTIFIER ::= { frnetserv 3 }
frnetservGroups OBJECT IDENTIFIER ::= { frnetservConformance 1 }
frnetservCompliances OBJECT IDENTIFIER ::= { frnetservConformance 2 }
-- Compliance Statements
frnetservCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities
which have Frame Relay Network Service Interfaces."
MODULE -- this module
MANDATORY-GROUPS { frnetservLportGroup, frnetservMgtVCSigGroup,
frnetservPVCConnectGroup, frnetservPVCEndptGroup }
OBJECT frPVCConnectStatus
SYNTAX INTEGER { active(1) } -- subset of RowStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, and only one of the
six enumerated values for the RowStatus textual
convention need be supported, specifically:
active(1)."
::= { frnetservCompliances 1 }
T. Brown (editor) Expires 1/31/94 [Page 33]
Internet Draft Frame Relay Service MIB July 30, 1993
-- Units of Conformance
frnetservLportGroup OBJECT-GROUP
OBJECTS { frLportNumPlan, frLportContact, frLportLocation, frLportType,
frLportAddrDLCILen, frLportVCSigProtocol, frLportVCSigPointer }
STATUS current
DESCRIPTION
"A collection of objects providing information applicable
to a Frame Relay Logical Port."
::= { frnetservGroups 1 }
frnetservMgtVCSigGroup OBJECT-GROUP
OBJECTS { frMgtVCSigProced, frMgtVCSigUserN391, frMgtVCSigUserN392,
frMgtVCSigUserN393, frMgtVCSigUserT391, frMgtVCSigNetN392,
frMgtVCSigNetN393, frMgtVCSigNetT392, frMgtVCSigNetnN4,
frMgtVCSigNetnT3, frMgtVCSigLinkRelRespErrors, frMgtVCSigProtRespErrors,
frMgtVCSigInactiveResps, frMgtVCSigLinkRelInitErrors,
frMgtVCSigProtInitErrors, frMgtVCSigInactiveInits }
STATUS current
DESCRIPTION
"A collection of objects providing information applicable to the
Local In-Channel Signaling Procedures used for a UNI/NNI logical port."
::= { frnetservGroups 2 }
frnetservPVCConnectGroup OBJECT-GROUP
OBJECTS { frPVCConnectAdminStatus, frPVCConnectOperStatus, frPVCConnectLastChange,
frPVCConnectMaxFrameSize, frPVCConnectBc, frPVCConnectBe, frPVCConnectCIR,
frPVCConnectGenericPointer, frPVCConnectStatus }
STATUS current
DESCRIPTION
"A collection of objects providing information applicable
to a Frame Relay PVC connection."
::= { frnetservGroups 3 }
frnetservPVCEndptGroup OBJECT-GROUP
OBJECTS { frPVCEndptRcvdSigStatus, frPVCEndptInFrames, frPVCEndptOutFrames,
frPVCEndptInDEFrames, frPVCEndptOutDEFrames, frPVCEndptInDiscards,
frPVCEndptInOctets, frPVCEndptOutOctets }
STATUS current
DESCRIPTION
"A collection of objects providing information application
to a Frame Relay PVC end-point."
::= { frnetservGroups 4 }
T. Brown (editor) Expires 1/31/94 [Page 34]
Internet Draft Frame Relay Service MIB July 30, 1993
END
T. Brown (editor) Expires 1/31/94 [Page 35]
Internet Draft Frame Relay Service MIB July 30, 1993
9. Acknowledgments
This document was produced by the Frame Relay Service MIB
Working Groups:
Special thanks goes to the Frame Relay Forum Technical
Committee for its participation in writing this MIB.
T. Brown (editor) Expires 1/31/94 [Page 36]
Internet Draft Frame Relay Service MIB July 30, 1993
10. References
[1] Cerf, V., "IAB Recommendations for the Development of Internet
Network Management Standards", RFC 1052, NRI, April 1988.
[2] Cerf, V., "Report of the Second Ad Hoc Network Management
Review Group", RFC 1109, NRI, August 1989.
[3] Rose M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[4] McCloghrie K., and M. Rose, "Management Information Base for
Network Management of TCP/IP-based internets", RFC 1156, Hughes
LAN Systems, Performance Systems International, May 1990.
[5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", RFC 1157, SNMP Research,
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[6] McCloghrie K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets", RFC 1213,
Performance Systems International, March 1991.
[7] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International
Standard 8824, December 1987.
[8] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation One
(ASN.1), International Organization for Standardization,
International Standard 8825, December 1987.
[9] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
RFC 1212, Performance Systems International, Hughes LAN Systems,
March 1991.
[10] K. McCloghrie and F. Kastenholz, Evolution of Interfaces
Group of MIB-II, Internet Draft, May, 1993.
[11] K. R. Rodemann, Service Management Architecture for Virtual Connection Services,
Internet-Draft, July 1993.
T. Brown (editor) Expires 1/31/94 [Page 37]
Internet Draft Frame Relay Service MIB July 30, 1993
11. Security Considerations
Security issues are not discussed in this memo.
12. Authors' Addresses
Tracy A. Brown
Bell Communications Research
331 Newman Springs Road
P.O. Box 7020
Red Bank, NJ 07701-7020
Phone: (908) 758-2107
EMail: tacox@mail.bellcore.com
T. Brown (editor) Expires 1/31/94 [Page 38]
Internet Draft Frame Relay Service MIB July 30, 1993
Table of Contents
1 Status of this Memo ................................... 1
2 Abstract .............................................. 1
3 The SNMPv2 Network Management Framework ............... 2
4 Object Definitions .................................... 3
5 Overview .............................................. 4
5.1 Apply MIB II to a Frame Relay Service ............... 7
5.2 Frame Relay Service MIB Terminology ................. 9
6 Object Definitions .................................... 12
6.1 The Frame Relay Service Logical Port Group .......... 13
6.2 The Frame Relay Management VC Signaling Group ....... 17
6.3 Frame Relay PVC Connection Group .................... 23
6.4 The PVC End-Point Group ............................. 28
7 Frame Relay Network Service TRAPS ..................... 32
8 Conformance Information ............................... 33
9 Acknowledgments ....................................... 36
10 References ........................................... 37
11 Security Considerations .............................. 38
12 Authors' Addresses ................................... 38
T. Brown (editor) Expires 1/31/94 [Page 39]